…and report

PresentationEditor now owns one FontResolver per document and passes it to the planner
(planRequiredFontFaces), the gate (which derives the family-path resolution from it and
resolves its report through it), and buildFontReport. So load, family resolution, and
diagnostics all go through the same per-document instance instead of the global default.

Behavior-preserving: with no runtime overrides the resolver matches the bundled map, and
the threaded params are optional (callers without a document context still use the global
functions). Measure and paint still use the global resolver + cache keys; threading those
(with the resolver signature in the measure cache key and paint reuse signature) is next.

…rsion docs

- Add FontResolver.reset() and call it from documentReplaced alongside the gate reset.
  The resolver is per PresentationEditor instance, so a reused editor must drop the prior
  document's runtime mappings or a fonts.map would leak into the next document.
- Fix the class JSDoc: the cache/reuse identity is the stable signature, not the numeric
  version (two docs at the same version with different mappings must not collide).

Measure and paint still use the global resolver; only planner, gate, and report read the
per-document instance so far. Reword the #fontResolver field and the gate fontResolver
option so they do not claim measure/paint consistency before that threading lands.

…tring)

measureBlock now accepts a resolvePhysical function and threads it through
measureParagraphBlock / measureListBlock / measureTableBlock / measureTabAlignmentGroup /
measureDropCap to buildFontString - including the table path's recursive measureBlock call
for cell content - so a document's text is MEASURED with its own resolver (honoring a
per-document fonts.map) instead of the global one. Defaults to the global bundled map, so
callers that pass nothing are unchanged; the body/header-footer callers that bind the
document resolver, plus the measure-cache font signature, come next.

Verified: measuring-dom tsc error profile is identical to baseline (no new errors vs the
pre-existing implicit-any/never backlog).

Thread the document FontResolver and its mapping signature through every
measure path - body, footnotes, header/footer, and per-rId header/footer -
so two editors that map the same logical family differently cannot share a
cached measure.

The signature rides a narrow incremental-layout runtime option (not the
exported LayoutOptions) and keys each measure cache; the resolver itself
rides the measure callback. previousMeasures reuse bypasses the cache key,
so it is now gated on the signature matching the prior pass. PresentationEditor
binds its resolver into the measure callback and records the signature its
measures were produced with.

Behavior-preserving: no public fonts.map yet, so the signature stays '' and
every path resolves through the bundled map as before. Paint is next.

The painter and the paint-reuse versioning now resolve fonts through the
document's per-instance FontResolver instead of the global one, completing the
per-document isolation the measure path already has.

The painter is per document, so its resolvePhysical comes from painter options
(PresentationEditor binds its resolver); text runs paint the family it returns,
the same one measurement used. The resolver's signature is folded into every
block's paint-reuse version - body via resolveLayout, header/footer via the
session - so a future fonts.map change repaints the way a font load does today.

Behavior-preserving: no public fonts.map yet, so the signature stays '' and
both paint output and reuse versions are byte-identical to before.

Two documents that map one logical family to different physical fonts must not
share a cached measure or reuse each other's painted DOM. The MeasureCache test
keys two signatures against one block; the resolveLayout test drives two real
resolvers (Georgia->Gelasio vs Georgia->Tinos) and asserts their block
paint-reuse versions differ. Both also assert the empty signature is
byte-identical to omitting it, locking in the behavior-preserving default.

…hreading

Two comments still said measure and paint do not read the per-document
resolver - true when written in the planner/gate phase, false now that both
resolve through it (a stale comment is a prompt-surface bug). Also soften two
"byte-identical to the prior global behavior" claims to "behavior-preserving
by construction": the signature is always '' and the resolver shares the
bundled map, so resolution is unchanged, though that is not golden-tested.